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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...