Installation

User Seed vs Passwd File

ephemeric
Contributor

Is there any difference in placing an `etc/passwd` file in place as opposed to using an `etc/system/local/user-seed.conf` during a scripted install?

As I understand it the `user-seed.conf` produces an `etc/passwd` if the latter doesn't exist and then the former is removed?

Labels (1)
0 Karma
1 Solution

dwaddle
SplunkTrust
SplunkTrust

I don't think there's a meaningful difference.  We drop pre-populated etc/passwd files all the time, and it just works.  You do have to restart Splunk for it to see the new passwd file.

View solution in original post

0 Karma

dwaddle
SplunkTrust
SplunkTrust

I don't think there's a meaningful difference.  We drop pre-populated etc/passwd files all the time, and it just works.  You do have to restart Splunk for it to see the new passwd file.

0 Karma

ephemeric
Contributor

I would say a passwd file is different in the way that it provides more options like mail address etc. as opposed to the seed file.

But in the end same but different.

0 Karma
Get Updates on the Splunk Community!

AppDynamics Summer Webinars

This summer, our mighty AppDynamics team is cooking up some delicious content on YouTube Live to satiate your ...

SOCin’ it to you at Splunk University

Splunk University is expanding its instructor-led learning portfolio with dedicated Security tracks at .conf25 ...

Credit Card Data Protection & PCI Compliance with Splunk Edge Processor

Organizations handling credit card transactions know that PCI DSS compliance is both critical and complex. The ...