HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SAMBA / CIFS messages
Operating System - HP-UX
1833876
Members
1609
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2009 01:25 PM
11-24-2009 01:25 PM
SAMBA / CIFS messages
Hello--
I am using smbclient every 8 minutes to put or get files from a Windows server. The script is run via cron and sends stdout and stderr to the same log file so cron does not send an email with the output.
Unfortunately, cron sends me an email message with this entry anyway:
Domain=[WINDOMAIN] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2]
Is there some way to tell SAMBA/CIFS to be quiet so that I am not receive this message every 8 minutes?
I am using smbclient every 8 minutes to put or get files from a Windows server. The script is run via cron and sends stdout and stderr to the same log file so cron does not send an email with the output.
Unfortunately, cron sends me an email message with this entry anyway:
Domain=[WINDOMAIN] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2]
Is there some way to tell SAMBA/CIFS to be quiet so that I am not receive this message every 8 minutes?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2009 01:30 PM
11-24-2009 01:30 PM
Re: SAMBA / CIFS messages
Shalom,
1) take a look at the cron entry. Maybe the output is going to | mailx and it should go to /dev/null
2) Take a look at smb.conf see if the log level is turned up. Change it to zero. Restart the service.
If this does nto work, I am out of ideas.
SEP
1) take a look at the cron entry. Maybe the output is going to | mailx and it should go to /dev/null
2) Take a look at smb.conf see if the log level is turned up. Change it to zero. Restart the service.
If this does nto work, I am out of ideas.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-24-2009 04:44 PM
11-24-2009 04:44 PM
Re: SAMBA / CIFS messages
Can you cut/paste your crontab entry? Also, as SEP suggested, look at you smb.conf to see what log level is set to.
Chances are good there's a problem with your crontab entry as you said it redirs stdout and stderr to the same log... but if it did, you shouldn't get the output emailed when the job runs.
-denver
Chances are good there's a problem with your crontab entry as you said it redirs stdout and stderr to the same log... but if it did, you shouldn't get the output emailed when the job runs.
-denver
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2009 08:34 AM
11-25-2009 08:34 AM
Re: SAMBA / CIFS messages
The cron entry is just the script. So any stdout or stderr will be sent to root by email.
I think that I have found the source of the text. After more research, not all of the scripts are producing the dreaded output, only half of them. There is one "smbclient" line in which the stderr is not redirected to a file:
smbclient "$share" "$pass" -D "$ntdir" -c "$command" | awk '{print $1}' \
| egrep "^u[0-9]+$" > $tmp
I will append " 2>&1 " and test. Stay tuned...
I think that I have found the source of the text. After more research, not all of the scripts are producing the dreaded output, only half of them. There is one "smbclient" line in which the stderr is not redirected to a file:
smbclient "$share" "$pass" -D "$ntdir" -c "$command" | awk '{print $1}' \
| egrep "^u[0-9]+$" > $tmp
I will append " 2>&1 " and test. Stay tuned...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP